home *** CD-ROM | disk | FTP | other *** search
- miro Computer Products AG 01.08.1996
-
- Version 2.10
-
- Installation of miro drivers for Windows95:
- ===========================================
-
- Attention: New installation routine for miro Windows 95 drivers
- and miroWINTOOLS. Install the miro drivers and
- miroWINTOOLS by running the install.exe program now.
-
- You can only use these miro Windows 95 drivers for the following miro graphics
- boards in a single screen solution:
-
- miroCRYSTAL 12SD
- miroCRYSTAL 20SD
- miroCRYSTAL 22SD
- miroCRYSTAL 20SV
- miroCRYSTAL 40SV
- miroMAGIC 20/40SV ergo
- miroMAGIC 80SV
- miroVIDEO 20SD
- miroVIDEO 22SD
- miroVIDEO 20SV
- miroVIDEO 40SV ergo
-
- Generally, dual screen solutions (Twinface), combinations of identical miro
- graphics boards or combinations with third party graphics
- boards are not supported !!!
-
-
- To install the miro drivers, proceed as follows:
- ================================================
-
- Installation of miro Windows 95 drivers and miroWINTOOLS
- ========================================================
-
- * If you have not done so already, start your computer
- * Click the Start menu
- * Click on the RUN... Icon
- * Enter the command A:\INSTALL
- * The miro*win install window opens
- * Select your desired language and click "Install"
- * The miro Windows 95 drivers and miroWINTOOLS will be copied to your system
- * The Settings folder appears.
- * Select Change Display Type... .The Change Display Type windows appears.
- Here you can change the graphics board and the monitor type.
- * To select another graphics board, click on the "Change" button.
- Now either "miro S3 Graphicadapter/PCI (DDRAW)" or
- "miro S3 Graphicadapter/VLB (DDRAW)"
- will be displayed.
- In case that both options are displayed, please select the model which
- is corresponding to your miro graphics board and click "Apply".
- The computer is restarted. After the restart the new resolutions are
- available.
-
- only miro Windows 95 drivers (without miroWINTOOLS)
- ===================================================
- * If you have not done so already, start your computer
- * Open the Control Panel
- * Click on Display
- * Click the Settings folder
- * Select Change Display Type... .The Change Display Type windows appears.
- Here you can change the graphics board and the monitor type.
- * To select another graphics board, click on the "Change" button.
- * Click "Have Disk..." To specify the disk drive from which you install
- the drivers: default is drive a:\.
- Now either "miro S3 Graphicadapter/PCI (DDRAW)" or
- "miro S3 Graphicadapter/VLB (DDRAW)"
- will be displayed. Please select the model which
- is corresponding to your miro graphics board and click "Apply".
- The computer is restarted. After the restart the new resolutions are
- available.
-
-
-
- Important hints for the installation:
- =====================================
-
- 1.) Don't try to use former miro Windows 3.xx drivers for Windows 95.
- In case you tried to use these drivers make sure that all former
- miro Windows 3.xx drivers and entries in your SYSTEM.INI file are removed.
-
- In the SYSTEM.INI you have to remove the complete entries in the section
- [928.drv], [Twin.right] and [Twin.left]. Delete the following files in Win95
- if available:
-
- Del \\OEMMAGS4.*
- Del \\OEMRAIN.*
- Del \\OEMCR32S.*
- Del \\OEMCR24S.*
- Del \\OEMCR16S.*
- Del \\OEMC16SI.*
- Del \\OEMCR8S.*
- Del \\OEMC10SD.*
- Del \\OEMC20SD.*
- Del \\OEMC20SV.*
- Del \\OEMC40SV.*
- Del \\OEMMAG40.*
- Del \\OEMMAG20.*
- Del \\OEMC20TW.*
- Del \\OEMBIBO*.*
- Del \\MAGS4*.DRV
- Del \\RAIN*.DRV
- Del \\CR32S*.DRV
- Del \\CR24S*.DRV
- Del \\CR16S*.DRV
- Del \\C16SI*.DRV
- Del \\C8S*.DRV
- Del \\1SD*.DRV
- Del \\C20SD*.DRV
- Del \\C20SV*.DRV
- Del \\C40SV*.DRV
- Del \\M20*.DRV
- Del \\M40*.DRV
- Del \\TW10*.DRV
- Del \\TW20*.DRV
- Del \\TWIN.DRV
- Del \\OCTO.MON
- Del \\OCTOVGA.*
- Del \\MAGIC_S4.BMP
- Del \\RAIN_WIN.BMP
- Del \\MINFO.TXT
- Del \\MWINTOOL.INI
- Del \\MSUP*.*
- Del \\MONSEL.*
- Del \\VIRTDLL.DLL
- Del \\MFONTCOM.EXE
- Del \\MIROSCOP.EXE
- Del \\MIROHOOK.DLL
- Del \\MSCOPE*.HLP
- Del \\MPWRSAVE.SCR
- Del \\TWIN*.*
- Del \\MTINT*.*
- Del \\MSIZE*.*
- Del \\WSIZER.*
- Del \\WADJUST.*
- Del \\MIROLOGO.RLE
-
- Also delete the miroWINTOOL program group and the icons
- on your Windows95 desktop!!!
-
- 2.) In case you are using a miro monitor or a common model please install
- a new monitor file. This installation disk contains this monitor.inf file.
- Make sure that there is no older OEM*.INF monitor file in your Win95\INF
- subdirectory. This subdirectory is hidden, but you can make it visible
- by entering the DIR /a command. All INF files are ASCII files and you
- can read these files with every editor, so please make sure that you
- don't delete required INF files. Look into the file before you delete it!!!
- If you are using the miro monitor files of the original Windows 95 CD,
- please use the miro monitor file of this disk.
-
- 3.) Every time you install new display drivers in Windows 95 a new OEM*.INF
- file will be copied into your WIN95\INF subdirectory. Windows 95 doesn't
- remove the old *.inf files. Make sure that only the specified OEM*.INF
- file is available. This could prevent many problems!
-
- 4.) Remember that all miroVIDEO graphics boards (VIDEO 20SD, VIDEO 20SV,
- VIDEO 22SD, VIDEO 40SV ergo) need an IRQ.
-
- 5.) In case Windows 95 doesn't start VLB computers, you can change the base
- address for the linear memory adressing:
-
- System.ini:
- [Display]
- LinBase=<Address> (MB)
-
- i.e. 64, 128, or 192
-
- 6.) For miroVIDEO graphics boards (VIDEO 20SD, VIDEO 20SV,
- VIDEO 22SD, VIDEO 40SV ergo) you can switch the hardware
- scaler off or improved.
- The entries are as follows:
-
- System.ini
- [Display]
- VideoStretch=<Value>
-
- Default values:
- greatest security : 257
- best video + security : 259
- best display quality + security : 771
- greatest performance : 261 <standard>
- best display quality + performance : 775
-
- The value can be calculated as follows:
- [0 / 1] for DIB scaling by hardware [off / on]
- + [0 / 2] for DIB interpolation by hardware [off / on]
- + [0 / 4] for DIB scaling parameter adaption [off / on]
- + [0 / 256] for DDB scaling by hardware [off / on]
- + [0 / 512] for DDB interpolation by hardware [off / on]
-
- 7.) A DIB engine driver is not usable for Video for Windows, but the
- optimized drivers can be fully used, if the miroPINBOARD will set the
- entries depending on the selected display mode in the Win.ini file.
-
- ->If possible, start the miroPINBOARD always starting Windows 95.
- The miroPINBOARD will correct the entries of Video for Windows
- automatically.
-
-
- 8.) Using the miroPINBOARD it may happen that switching from the
- virtual modes to the real modes doesn't work at once. In this case we
- recommend to switch into the real mode resolution (640 x 480) first and
- after this to a higher resolution.
-
-
- 9.) If it happens that both bus adapter versions will be displayed. Make sure
- that you select the right bus interface that means either PCI, or VLB,
- depending of the bus interface of your miro graphics board. Otherwise the
- miro graphics board can't be installed for Windows 95 and the drivers
- won't work.
-
- 10.)Combination of miroVIDEO DC20 and S3 based graphics boards in mainboards
- with AWARD BIOS:
- 868 and 968 S3 chips etc. need a linear adress area of 64MB under Windows 95.
- The current AWARD BIOS reserves an address area of 32MB for this graphics
- boards only. In case the memory area of the miroVIDEO DC20 is located directly
- after the memory area of the S3 based graphics board make sure that there is
- a memory area of 64MB between the graphics board and the miroVIDEO DC20
- memory area. You can change the memory area in Windows 95 in your System
- Control Panel in the Device Manager in the Resources tab.
-
- AWARD has solved this problem with a BIOS update. This BIOS Update can be
- loaded down from the BBS of the motherboard manufacturers.
-
- 11.)During the installation of Lotus Smart Suite 4.0 under Windows 95 the
- background bitmap of Lotus won't be displayed properly, but there are no
- limitations using the functions of this software package. In the next
- driver release this bug will be fixed.
-